Repository navigation
canvas: expose erwin XML in the Export menu - #61
Merged
Merged
Conversation
The erwin exporter shipped CLI-only (mdl export erwin); the canvas Export dropdown — where
users actually export — didn't offer it, so the feature wasn't discoverable in the UI.
The menu is data-driven (it renders whatever GET /api/export returns), so the fix is server
side: add erwin to the advertised format list and to the /api/export/{fmt} dispatch (using the
project's export.erwin.naming config, same as the CLI; application/xml, .xml filename). No
canvas rebuild needed — the existing bundle picks it up from the API.
Verified live: 'erwin XML' now appears in the Export dropdown and downloads an XSD-valid
document (<model>.xml). Tests: /api/export lists erwin; /api/export/erwin returns an XML
attachment. Server suite 233 passed.
dbose
added a commit
that referenced
this pull request
Nov 1, 2026
0.8.0 -> 0.8.1 (patch). Exposes the erwin exporter in the canvas Export dropdown (PR #61) — UI wiring of the already-shipped 'mdl export erwin' feature, so a patch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
mdl export erwinshipped (PR #60) but CLI-only — the canvas Export dropdown, where users actually export, didn't list it. A format reachable only by typing a CLI command isn't really exposed to users. (Screenshot in the issue showed SQL DDL / Mermaid / DBML / CSV / Data contract / Cypher, but no erwin.)What
The Export menu is data-driven — it renders whatever
GET /api/exportreturns — so the fix is server-side:{"id": "erwin", "label": "erwin XML"}to the advertised format list.erwinbranch to/api/export/{fmt}, using the project'sexport.erwin.namingconfig (same as the CLI), served asapplication/xmlwith a<model>.xmlfilename.No canvas rebuild — the existing bundle picks it up from the API; the import side already listed erwin.
Verified live
<model>.xml./api/export/erwin→ 200,application/xml,Content-Disposition: attachment; filename="<model>.xml", body validates againsterwin/ERwinSchema.xsd.Tests
/api/exportlistserwin;/api/export/erwinreturns an XML attachment starting with<?xmlandFormat="erwin". Server suite 233 passed, ruff clean.